connections.ev3: Improve firmware update. #98
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Allow faster flashing of smaller firmwares by erasing only as much as needed. - Work around USB3.0 issues with the EV3 bootloader.
|
Rats, I have a re-freshed clone on linux and wanted to test USB-2 flash. It works, but I am not sure if i use the updated version. I ran in the activated .venv in the git clone on an USB-2 plug: In ERASE_TICKS = 60So looks good, but . . . Bert |
Member
Author
|
@BertLindeman, this is an update for EV3. There were no changes for NXT. |
Hard to read ;-) Thanks |
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 16, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the hardware version can still be read even when the brick is plugged into a USB 3.0 port. Unforunately, the CRC packets likely cannot be salvaged this way - the CRC request is longer than the CRC response and so the CRC value is overwritten inside the brick.
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 20, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the hardware version can still be read even when the brick is plugged into a USB 3.0 port. Unforunately, the CRC packets likely cannot be salvaged this way - the CRC request is longer than the CRC response and so the CRC value is overwritten inside the brick.
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 20, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the hardware version can still be read even when the brick is plugged into a USB 3.0 port. Unforunately, the CRC packets likely cannot be salvaged this way - the CRC request is longer than the CRC response and so the CRC value is overwritten inside the brick.
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 20, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the hardware version can still be read even when the brick is plugged into a USB 3.0 port. Unforunately, the CRC packets likely cannot be salvaged this way - the CRC request is longer than the CRC response and so the CRC value is overwritten inside the brick.
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 20, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the EEPROM version can still be read even when the brick is plugged into a USB 3.0 port. Unforunately, the CRC packets likely cannot be salvaged this way - the CRC request is longer than the CRC response and so the CRC value is overwritten inside the brick.
JakubVanek
added a commit
to JakubVanek/ev3duder
that referenced
this pull request
Jun 21, 2025
As noted in the linked commit (coming from pybricks/pybricksdev#98), the EEPROM version can still be read even when the brick is plugged into a USB 3.0 port.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since all of the changes could be done without any low level hacking of the HID API, this is very promising for when we make a web-based version in the future.
Changes have not been tested on a USB2.0 system yet, but there should be no changes.
Tested on a copy of the official firmware (16MiB).
And on a 1.5MiB Pybricks firmware, which now takes about 6 seconds to erase and 6 seconds to install, instead of up to two minutes or more.